fix(tcloud-release): wait for npm publication processing - #64

Problem

npm accepted TCloud 0.8.0 and signed its provenance in run 36671321028, attempt 1. npm said processing could take a few minutes. The verifier stopped after six checks and five ten-second waits. The package appeared later; attempt 2 succeeded.

Change

Extend the existing loop to 31 reads and 30 ten-second waits. Exact hash checks, existing-version behavior and trusted publishing are unchanged. No version or access changes.

Evidence

• The exact maintained publication step verified public TCloud 0.8.0 against the reviewed candidate: SHA1 6284f2620e94bcb377e5fe158f5c19db0cee26a2.
• Public tarball matches the reviewed candidate byte for byte: SHA256 2b946cf008817b1bcc49c2ebdb50d70d73824320ede8773ea74b046eef22fefe.
• YAML parsing, Bash syntax, all eight existing script checks and normal commit/push hooks passed.
• Independent review approved the exact three-line diff over 945d452dac715ae38da6822465ee6b40ff9d58d8: 31 checks, 300 seconds of retry waits, with unchanged rejection of different bytes.
• Publication run is terminal success on attempt 2.

Risk and recovery

A missing package takes longer to fail verification. Different package bytes still fail immediately. Reverting restores the old wait limit.